home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000032_icon-group-sender_Mon Sep 16 16:24:02 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
3KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id g8GNNiA09185
for icon-group-addresses; Mon, 16 Sep 2002 16:23:44 -0700 (MST)
Message-Id: <200209162323.g8GNNiA09185@baskerville.CS.Arizona.EDU>
From: Christopher Browne <cbbrowne@acm.org>
X-Newsgroups: comp.lang.icon
Subject: Re: Icon Wish 2
Date: 16 Sep 2002 22:52:42 GMT
X-Draft-From: ("nnvirtual:Languages" 928)
X-Home-Page: http://www.cbbrowne.com/info/
X-Emacs-Acronym: Everyday Material Almost Compiled Successfully
Microsoft: We've got the solution for the problem we sold you.
X-Uboat-Death-Message: BLOWN UP BY EIGHT DESTROYERS. EXPLODING. U-704.
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
In the last exciting episode, No spam <complaint@nospam.org> wrote::
> Gene Kahn wrote:
>> An "Icon.NET", as in VB.NET, is my informal and short name for an
>> implementation of Icon running inside the Microsoft .NET
>> environment.
>
> Yes, but if .NET is not adopted outside the Microsoft realm, use of
> it would be highly non-portable ...?
There seem to be two other implementations of the ".NET VM," which
/could/ be a counterargument. But I doubt they will be /realistic/
alternatives to .NET anymore than the "UNIX port" of DCOM made it
realistic to deploy COM-based applications on UNIX.
The reason is that Microsoft isn't going to have the environment start
and end with the VM. They will actively encourage users to write
applications that employ extensive references to components that will
only be available on Windows. Anything GUI would represent an
/excellent/ example of this, for instance. They'll be more than happy
to provide .NET interfaces to Win32, perhaps even having that "linked
in" by default, and that will only be available on Windows.
It would seem to me to make a /lot/ more sense to try to deploy Icon
atop the upcoming Perl "Parrot" bytecode system. Consider that:
a) It /is/ intended to be portable;
b) There is intent for it to be not /totally/ Perl-oriented, as the
Python and Ruby communities have had discussions about cooperation;
c) It is not inconceivable that you could submit changes to Parrot to
the Perl team, and have /some/ hope of them being accepted.
--
(concatenate 'string "cbbrowne" "@ntlug.org")
http://cbbrowne.com/info/bytecode.html
You know that little indestructible black box that is used on
planes---why can't they make the whole plane out of the same
substance?